…P-42)

Ship the first, fully-deterministic slice of the roadmap-#19 benchmark: the
token-reduction numbers behind the "massive token savings" claim. Reuses the
frozen Spec 065 tool corpus (45 tools, 7 reference servers) as a versioned,
non-drifting universe and tiktoken cl100k_base (already a dep) as a
reproducible model-agnostic estimator.

Compares the three routing modes' static context cost:
- baseline (all upstream tools loaded directly)
- retrieve_tools (BM25 discovery + call_tool variants)
- code_execution (orchestration + retrieve_tools)

over the corpus and reports per-mode savings. Real proxy tool defs are captured
verbatim from internal/server/mcp.go into bench/proxy_tools_v1.json (provenance
recorded). Emits report.json + a self-contained dashboard.html (gitignored;
reports never committed, per Spec 065 CN-003).

Conservative by construction: input schemas excluded uniformly understates the
baseline, so measured savings (65.5% / 70.3% on the 45-tool corpus) are a floor.

Methodology, limitations, and the scoped-but-not-yet-built follow-ups (live run
with full schemas + accuracy/latency, LLM e2e, CI publish) are in bench/README.md.

Related #MCP-42

Co-Authored-By: Paperclip <noreply@paperclip.ing>

… smoke test

KimiReviewer finding 2: code_execution is at line 626 in mcp.go at 89f06b5,
not 675 as claimed. Line numbers drift with unrelated edits and the actual
function names are the stable identifier — remove all line numbers from the
provenance comment to prevent future rot.

KimiReviewer finding 3: add TestWriteReports_SmokeTest covering WriteReports
output (JSON round-trips to Report, HTML is non-empty and contains all mode
names). All 5 tests pass; golangci-lint v2 clean.

Related #MCP-42

Co-Authored-By: Paperclip <noreply@paperclip.ing>

…cl. management tools (MCP-3161)

The token-reduction benchmark scored only 6 hand-maintained proxy tools and
omitted the shared management tool set (upstream_servers, quarantine_security,
search_servers, list_registries) that both routing modes append via
buildManagementTools. That undercounted the proxy-mode context cost and
inflated the headline savings (Codex finding on PR #747).

Replace bench/proxy_tools_v1.json with server.ProxyModeToolDefs, which builds
the catalog from the live builders (buildCallToolModeTools /
buildCodeExecModeTools in internal/server/mcp_routing.go) so it can never drift
from production and always reflects the tools the agent actually sees. This
also fixes a second drift: the fixture's retrieve_tools descriptions did not
match the per-mode builder descriptions.

Corrected figures over the 45-tool Spec 065 corpus (name+description only):
retrieve_tools ~17% (10 tools), code_execution ~43% (6 tools). Updated README
and notes; the schema-exclusion claim is no longer unambiguously conservative
now that large-schema management tools are in the proxy cost.

Tests: bench asserts both modes include the 4 management tools; internal/server
pins ProxyModeToolDefs to the builders so the catalog can't silently drift.

Related #747